Using Dublin Core

Label: AbstractTerm description: A summary of the content of the resource.Guidelines for creation of content: Used when a description of a resource consists of a formal abstract. For implementations where formal abstracts arepreferred, using the specific term allows the label to better reflect the level of the description.Examples: Abstract="This article describes the work of the IFB Chaos Committee, including a summary of its majorfindings."="This article describes the work of the IFB Chaos Committee, including a summary of its majorfindings." Refinement(s) for element: Date Date refinements are generally useful in situations where more than one date is needed, and the difference between thedates may be important to users. Note that the first five Date refinement terms were among the earlier ones approvedby DCMI, and the naming convention of the time was not to include "date" as part of the refined term. The most recentones reflect changes in the naming convention used, in which the name of the refined term expresses more clearly therelationship to the parent element. When using date refinements it can be unwise to insert a text string that repeats thedistinction created by the refinement itself. For instance, the string "Valid 20010211" in a statement where therefinement "valid" is used might show up in a labelled display as: VALID: Valid 20010211. CreatedLabel: CreatedTerm description: Date of creation of the resource.Guidelines for creation of content: If the date of creation of the resource is known, and that date is important to note specifically (e.g., there are otherrelevant dates to record), use the term Created for the creation date of the resource. Note that the "one-to-one" rulerequires that the creation date be that of the resource being described, not any early version from which the currentresource is derived. ValidLabel: ValidTerm description: Date (often a range) of validity of a resource.Guidelines for creation of content: If the resource is only valid or relevant for a particular date or range of dates, the term Valid may be used to expressthose dates. This may be particularly important if the resource will be retained over time but its use is valid only during aparticular period or until a particular date. AvailableLabel: AvailableTerm description: Date (often a range) that the resource will become or did become available.Guidelines for creation of content: In general, the term Available should be used in the case of a resource for which the date of availability may be distinctfrom the date of creation, and the date of availability is relevant to the use of the resource. IssuedLabel: Issued Using Dublin Core Dublin Core Qualifiersfile:///E:/aaa_DL_FUB/Support%20Material/DCMI/Using%20Dubli... 5 di 1031/03/2008 20.15Term description: Date of formal issuance (e.g., publication) of the resource.Guidelines for creation of content: The term Issued should be applied when a formal date of issuance or publication is relevant to the resource, and isdistinct from other dates that may be used with the resource. ModifiedLabel: ModifiedTerm description: Date on which the resource was changed.Guidelines for creation of content: Modified dates may be used to record either all instances of modification or only the latest. When only one modified dateis recorded, it is assumed to be the latest. dateAcceptedLabel: Date AcceptedTerm description: Date of acceptance of the resource (e.g. of thesis by university department, of article by journal, etc.).Guidelines for creation of content: If, in the lifecycle of a resource, the date of acceptance by a formal body or entity is relevant to the use of the resource,dateAccepted may be used. dateCopyrightedLabel: Date CopyrightedTerm description: Date of a statement of copyright.Guidelines for creation of content: If, in the lifecycle of a resource, the date of copyright is relevant to the use of the resource, dateCopyrighted may beused. dateSubmittedLabel: Date SubmittedTerm description: Date of submission of the resource (e.g. thesis, articles, etc.).Guidelines for creation of content: If, in the lifecycle of a resource, the date of submission to a body or entity is relevant to the use of the resource,dateSubmitted may be used. Refinement(s) for element: Format ExtentLabel: ExtentTerm description: The size or duration of the resource.Guidelines for creation of content: Because the refinement Extent is used in a variety of situations, it generally consists of both a numeric value and acaption that is needed to interpret the numeric value. Best practice is to separate the numeric value and the caption witha space, whether the caption appears before or after the value.Examples: Extent="folio"Extent="899 Kb"Extent="21 minutes" MediumLabel: MediumTerm description: The material or physical carrier of the resource.Guidelines for creation of content: Medium is generally used when the resource is of a physical nature, for instance a painting or model, where the physical Using Dublin Core Dublin Core Qualifiersfile:///E:/aaa_DL_FUB/Support%20Material/DCMI/Using%20Dubli... 6 di 1031/03/2008 20.15carrier or material used is relevant to the user. For instance, if the resource is a movie on DVD, and is only available as aphysical object, it should be described as such. If it is available digitally, for download or presentation on a website, itsformat would be reflected in the Format element. Note that, because of the physical nature of materials described withthis refinement, the encoding scheme "IMT" is not valid for use with Medium.Examples: Medium="cotton fabric with sequins"Medium="bronze on wooden pedestal"Medium="oil on wood" Refinement(s) for element: Relation Most of the refinements of Relation are expressed as "reciprocals" and may be used to link resources in two directions,though this is not required. Implementors need not describe both or all resources involved in a reciprocal relationship toexpress the relationship--in other words, they may describe a later version and relate it to the earlier without having theneed or opportunity to describe the earlier, and vice versa. In some of the relationships below, maintaining reciprocalityis more important. In others, one direction of the relationship is more relevant that the other. These differences will bementioned in the guidelines for specific terms. In All cases, either a string or a URI may be used as a value. If a URI is used, the scheme should be designated. Examples for Relation refinements can be found with the Relation element. When using Relation refinements, do not useembedded text labels, as the examples illustrate. isVersionOfLabel: Is Version OfTerm description: The described resource is a version, edition, or adaptation of the referenced resource. Changes inversion imply substantive changes in content rather than differences in format. Guidelines for creation of content: Use only in cases where the relationship expressed is at the content level. Relationships need not be close for therelationship to be relevant. "West Side Story" is a version of "Romeo and Juliet" and that may be important enough inthe context of the resource description to be expressed using isVersionOf. The Broadway Show and the movie of "WestSide Story" also relate at a similar level, but the video and DVD of the movie are more usefully expressed at the level offormat, the content being essentially the same. See also isFormatOf. hasVersionLabel: Has VersionTerm description: The described resource is a version, edition, or adaptation of the referenced resource. Changes inversion imply substantive changes in content rather than differences in format.Guidelines for creation of content: See isVersionOf for basic guidelines. isReplacedByLabel: Is Replaced ByTerm description: The described resource is supplanted, displaced, or superseded by the referenced resource.Guidelines for creation of content: When establishing a chain of versions, where only one version is valid, the use of isReplacedBy and Replaces allows therelationship to be expressed and the user directed to the appropriate version. In this case, the reciprocal relationshipsare quite important. ReplacesLabel: ReplacesTerm description: The described resource supplants, displaces, or supersedes the referenced resource.Guidelines for creation of content: See isReplacedBy for basic guidelines. isRequiredByLabel: Is Required By Using Dublin Core Dublin Core Qualifiersfile:///E:/aaa_DL_FUB/Support%20Material/DCMI/Using%20Dubli... 7 di 1031/03/2008 20.15Term description: The described resource is required by the referenced resource, either physically or logically.Guidelines for creation of content: In the case of IsRequiredBy and Requires, there is a clearer need to express the Requires relationship than theIsRequiredBy, though both can be useful. This relationship is most often seen in relationships between software anddocuments or applications and hardware and/or software requirements. RequiresLabel: RequiresTerm description: The described resource requires the referenced resource to support its function, delivery, or coherenceof content.Guidelines for creation of content: See isRequiredBy for basic guidelines. isPartOfLabel: Is Part OfTerm description: The described resource is a physical or logical part of the referenced resource.Guidelines for creation of content: The isPartOf and hasPart relationships are essentially "parent/child" relationships--hierarchical in nature. With them canbe expressed both one-to-one and one-to-many types of relationships. hasPartLabel: Has PartTerm description: The described resource includes the referenced resource either physically or logically.Guidelines for creation of content: See isPartOf for basic guidelines. isReferencedByLabel: Is Referenced ByTerm description: The described resource is referenced, cited, or otherwise pointed to by the referenced resource.Guidelines for creation of content: The isReferencedBy and References refinements enable the expression of relationships that aid the user but are notnecessary tied to the lifecycle or necessary for the intended use of the resource. This relationship might be used to linkan article critical of a resource to that resource, a satire of a speech to the original speech, etc. ReferencesLabel: ReferencesTerm description: The described resource references, cites, or otherwise points to the referenced resource.Guidelines for creation of content: See isReferencedBy for basic guidelines. isFormatOfLabel: Is Format OfTerm description: The described resource is the same intellectual content of the referenced resource, but presented inanother format.Guidelines for creation of content: This relationship is explicitly for the expression of relationships between resources for which format is the primaryvariable. Because Dublin Core maintains the principle of "one-to-one," each resource is expected to have its owndescription. See also isVersionOf. hasFormatLabel: Has Format Using Dublin Core Dublin Core Qualifiersfile:///E:/aaa_DL_FUB/Support%20Material/DCMI/Using%20Dubli... 8 di 1031/03/2008 20.15Term description: The described resource pre-existed the referenced resource, which is essentially the same intellectualcontent presented in another format. Guidelines for creation of content: See isFormatOf for basic guidelines. conformsToLabel: Conforms ToTerm description: A reference to an established standard to which the resource conforms.Guidelines for creation of content: The standards referenced might be educational standards, accessibility standards, or any other established standard thatis relevant to the use of the resource. Refinement(s) for element: Coverage SpatialLabel: SpatialTerm description: Spatial characteristics of the intellectual content of the resource.Guidelines for creation of content: Spatial characteristics may include geographic names, latitude/longitude, or other established georeferenced values.Clearly, this refinement does not allow complex or sophisticated georeferencing, but attention to standard schemes andcontrolled vocabularies should provide useful results. Controlled vocabulary terms can be drawn from recommendedvocabularies, or standard labelling within the value can provide useful assistance to users and applications. For additionalinformation on encoding spatial information see the DCMI Box Encoding Scheme and the DCMI Point Encoding Scheme.Examples: Spatial="Chicago, Ill."Spatial="Lat: 44 00 00 S Long: 068 00 00 W Name: Patagonia"Spatial="Upstate New York" TemporalLabel: TemporalTerm description: Temporal characteristics of the intellectual content of the resource.Guidelines for creation of content: Temporal characteristics include those aspects of time that relate to the intellectual content of a resource and not itslifecycle. Examples might include a resource describing some aspect of the 19th century but itself created this year. Inthat case, the Temporal Coverage would be the 19th century, and the Date (or Date Created) would be 2003. Values canbe text strings or encoded values. Specific suggestions for encoding Temporal characteristics may be found in the DCMIPeriod Encoding Scheme.Examples: Temporal="Jurassic Period"Temporal="1922-1978"Temporal="Twentieth Century" Refinement(s) for element: Audience MediatorLabel: MediatorTerm description: A class of entity that mediates access to the resource and for whom the resource is intended or useful.The audiences for a resource are of two basic classes: (1) an ultimate beneficiary of the resource, and (2) frequently, anentity that mediates access to the resource. The mediator element refinement represents the second of these twoclasses.Guidelines for creation of content: In an educational setting, a teacher might be designated the Mediator for a resource intended for use by a teacher in aclassroom of students of a particular level or sharing other similar characteristics. Resources intended to be used directlyby those same students would not include a Mediator. Mediators may be expressed in more or less specific terms,depending on the needs of the implementation. Controlled vocabularies can be useful in distinguishing Mediators.Examples: Using Dublin Core Dublin Core Qualifiersfile:///E:/aaa_DL_FUB/Support%20Material/DCMI/Using%20Dubli... 9 di 1031/03/2008 20.15Mediator="Reading specialist"Mediator="ESL teachers" educationLevelLabel: Education LevelTerm description: A general statement describing the education or training context. Alternatively, a more specificstatement of the location of the audience in terms of its progression through an education or training context.Guidelines for creation of content: Commonly, this term would be used for a grade level for materials intended for an educational setting. Although nospecific controlled vocabulary has been recommended for use with educationLevel, consistent use of terminology orreliance on an available controlled vocabulary enables more consistent results.Examples: educationLevel="elementary school students"educationLevel="4th-5th grade"educationLevel="secondary science" Refinement(s) for element: Rights accessRightsLabel: Access RightsTerm description: Information about who can access the resource or an indication of its security status. Access Rightsmay include information regarding access or restrictions based on privacy, security or other regulations.Guidelines for creation of content: Access rights is intended to allow the characterization of restrictions to view, search or use resources, based onattributes of the resource itself or the class or category of user. An example would be a resource that was restricted tousers holding a particular security clearance, or one that required login or authentication at a particular website.Examples: accessRights="Available to subscribers only."accessRights="Viewable by Medium security cleared staff only." licenseLabel: LicenseTerm description: A legal document giving official permission to do something with the resource. Recommended bestpractice is to identify the license using a URI. Examples of such licenses can be found athttp://creativecommons.org/licenses/.Guidelines for creation of content: License is designed to allow the inclusion of specific licensed uses to be specified. An example would be a resource thatwas available to be used freely but not for reproduction within commercial applications.Examples: license="http://creativecommons.org/licenses/by-nc-nd/2.0/ legalcode"license="Licensed for use under Creative Commons Attribution 2.0." Refinement(s) for element: Identifier bibliographicCitationLabel: Bibliographic CitationTerm description: A bibliographic reference for the resource. Recommended practice is to include sufficient bibliographicdetail to identify the resource as unambiguously as possible, whether or not the citation is in a standard form.Guidelines for creation of content: Because this term is not describing a relationship to another resource, it should be limited to citations to the resourcedescribed in the remainder of the record. For instance, if the resource is an article for a journal, it is appropriate toinclude very specific information about the article, even page references, if such information is used to cite the article ina standard format for reference by other resources, even if the article being described is in a digital format.Examples: bibliographicCitation="ESOP, v.2, no. 1, Apr. 2003, p. 5-8" Using Dublin Core Dublin Core Qualifiersfile:///E:/aaa_DL_FUB/Support%20Material/DCMI/Using%20Dubli... 10 di 1031/03/2008 20.15bibliographicCitation="Nature, v.87, p. 200" For additional guidance on using this refinement, see: Guidelines for Encoding Bibliographic Citation Information inDublin Core. Copyright © 1995-2008 DCMI. All Rights Reserved. Using Dublin Corefile:///E:/aaa_DL_FUB/Support%20Material/DCMI/Using%20Dubli... 1 di 231/03/2008 20.15Using Dublin Core Appendix, Roles Date Issued: 2005-12-07Identifier: http://dublincore.org/documents/2005/12/07/usageguide/appendix_roles.shtmlReplaces: http://dublincore.org/documents/2005/11/07/usageguide/appendix_roles.shtmlIs Replaced By: Not ApplicableIs Part Of: http://dublincore.org/documents/2005/11/07/usageguide/Latest version: http://dublincore.org/documents/usageguide/appendix_roles.shtmlTranslations: http://dublincore.org/resources/translations/Status ofdocument:DCMI Recommended Resource Description ofdocument:This document describes the use of a subset of the MARC Relator list as a source of role propertiesfor Qualified Dublin Core. 6. Using Agent Roles in Dublin Core